Repository navigation
Import GitHub OSV advisories incrementally - #2498
Open
Prachi194agrawal wants to merge 1 commit into
Open
Prachi194agrawal wants to merge 1 commit into
Prachi194agrawal wants to merge 1 commit into
Conversation
Signed-off-by: Prachi Agrawal <prachi194agrawal@gmail.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to #2317
The GitHub OSV importer currently scans and processes every reviewed advisory on each run. This PR adds an incremental import prototype that processes added and changed advisory files after the first successful import.
The importer stores the last successfully imported commit in a
GitImportCheckpointfor the pipeline and repository. On later runs, it compares that commit with the current checkout and selects changed JSON files. If the previous commit is unavailable or the history has diverged, it falls back to a full import.Deleted advisory paths are logged for review, while existing records and their history are retained. The checkpoint advances only after importing the selected advisories and cleaning up the checkout successfully. Failed runs keep the previous checkpoint so the changes can be retried.
This prototype reduces advisory parsing and database work for
github_osv_importer_v2. It retains the existing clone process. Deletion handling and checkpoint timing can be reviewed before extending the approach to other importers.Testing
The tests use a local Git repository to cover first and incremental imports, unchanged and deleted files, missing or rewritten history, renames, and failure and retry behavior.
Result: 15 passed, 5 warnings.
The new migration was also applied locally with

venv/bin/python manage.py migrate.